Account replication including security configurations

ABSTRACT

A request to replicate a first account maintained by a data platform is received. Based on the request, account data associated with the account is accessed. The account data comprises security configurations for the first account. In response to the request, the first account is replicated using the account data. A second account results from replicating the first account. The replicating of the first account comprises automatically replicating the security configurations for the first account to the second account. The replicating of the security configurations comprises replicating an identity management configuration of the first account; replicating an authorization configuration of the first account; and replicating an authentication configuration of the first account.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.17/898,176, filed Aug. 29, 2022, which is a continuation of U.S. patentapplication Ser. No. 17/655,887, filed Mar. 22, 2022 and now issued asU.S. Pat. No. 11,494,500, which is a continuation of U.S. PatentApplication Ser. No. 17/643,642, filed Dec. 10, 2021 and now issued asU.S. Pat. No. 11,314,875, which claims priority to U.S. ProvisionalPatent Application No. 63/284,384 filed on Nov. 30, 2021, the contentsof which are incorporated herein by reference in their entireties.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to databases and, morespecifically, to replication of account security features for a multipledeployment database.

BACKGROUND

Data platforms are widely used for data storage and data access incomputing and communication contexts. With respect to architecture, adata platform could be an on-premises data platform, a network-baseddata platform (e.g., a cloud-based data platform), a combination of thetwo, and/or include another type of architecture. With respect to typeof data processing, a data platform could implement online transactionalprocessing (OLTP), online analytical processing (OLAP), a combination ofthe two, and/or another type of data processing. Moreover, a dataplatform could be or include a relational database management system(RDBMS) and/or one or more other types of database management systems.

In a typical implementation, a data platform includes one or moredatabases that are maintained on behalf of a customer account. Indeed,the data platform may include one or more databases that arerespectively maintained in association with any number of customeraccounts, as well as one or more databases associated with a systemaccount (e.g., an administrative account) of the data platform, one ormore other databases used for administrative purposes, and/or one ormore other databases that are maintained in association with one or moreother organizations and/or for any other purposes. A data platform mayalso store metadata in association with the data platform in general andin association with, as examples, particular databases and/or particularcustomer accounts as well.

Users and/or executing processes that are associated with a givencustomer account may, via one or more types of clients, be able to causedata to be ingested into the database, and may also be able tomanipulate the data, add additional data, remove data, run queriesagainst the data, generate views of the data, and so forth.

In an example implementation of a data platform, a given database isrepresented as an account-level object within a customer account, andthe customer account may also include one or more other account-levelobjects such as users, roles, and/or the like. Furthermore, a givenaccount-level database object may itself contain one or more objectssuch as tables, schemas, views, streams, tasks, and/or the like. A giventable may be organized as records (e.g., rows) that each include one ormore attributes (e.g., columns). A data platform may physically storedatabase data in multiple storage units, which may be referred to asblocks, micro-partitions, and/or by one or more other names.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the disclosure.

FIG. 1 illustrates an example computing environment that includes anetwork-based data platform in communication with a cloud storageprovider system, in accordance with some embodiments of the presentdisclosure.

FIG. 2 is a block diagram illustrating components of a compute servicemanager, in accordance with some embodiments of the present disclosure.

FIG. 3 is a block diagram illustrating components of an executionplatform, in accordance with some embodiments of the present disclosure.

FIG. 4 is a conceptual diagram illustrating various customer accountreplication groups, in accordance with some embodiments of the presentdisclosure.

FIGS. 5-8 are flow diagrams illustrating operations of the network-baseddata platform in performing a method for customer account replication,in accordance with some embodiments of the present disclosure.

FIG. 9 illustrates a diagrammatic representation of a machine in theform of a computer system within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, in accordance with some embodiments ofthe present disclosure.

DETAILED DESCRIPTION

Reference will now be made in detail to specific example embodiments forcarrying out the inventive subject matter. Examples of these specificembodiments are illustrated in the accompanying drawings, and specificdetails are set forth in the following description in order to provide athorough understanding of the subject matter. It will be understood thatthese examples are not intended to limit the scope of the claims to theillustrated embodiments. On the contrary, they are intended to coversuch alternatives, modifications, and equivalents as may be includedwithin the scope of the disclosure.

In some instances, it may be beneficial to replicate database dataacross multiple geographic locations, across multiple database vendorsor providers, and/or across multiple computing devices that may belocated in the same physical location or in two or more differentlocations. These multiple locations, vendors, providers, and/orcomputing devices may be referred to herein as “deployments.” This mayprovide significant benefits to a database client because the data isbacked up in more than one location. In the event that one deployment isunavailable due to, for example, a power outage, a system error, ascheduled maintenance downtime, and so forth, a failover process ensuresa different deployment takes over the management and operation of thedatabase.

In conventional data platforms, customer accounts can be replicatedacross multiple deployments. For a typical database with multipledeployments, account administrators must manually manage accountsecurity configurations to keep them in-sync across primary andsecondary accounts used for the failover. Further, end users mustmanually re-configure security configurations and re-authenticate allsecurity tokens when an account is replicated.

Aspects of the present disclosure include systems, methods, and devicesto address, among other problems, the aforementioned shortcomings ofaccount replication with conventional data platforms by using anapproach to account replication that involves automatically replicatingsecurity configurations from a primary account to a replicated account(also referred to herein as a “secondary account”). With this approachto account replication, any configuration changes made to the primaryaccount are also automatically replicated, thereby eliminating the needfor account administrators to manually manage the securityconfigurations in primary and secondary accounts to keep them in-sync.Also, end users connecting to the data platform can continue toseamlessly work when failover happens from primary to the secondaryaccount.

When replicating from a primary account to a secondary account inaccordance with the approach described herein, all existing securityconfigurations are seamlessly replicated. Meanwhile, all long-livedtokens generated by the primary account can be validated by thesecondary account. Thus, even if a failover or a recovery happens, endusers are not impacted.

In example embodiments, a data platform receives a request to replicatea primary account to a secondary account. Based on the request, the dataplatform accesses account data of the primary account. The account datacan include account-level objects such as users, roles, and the like, aswell as one or more security configurations. The security configurationscan include: an identity management configuration that defines user androle provisioning features for the primary account such as a System forCross-Domain Identity Management (SCIM) configuration; an authorizationconfiguration that defines resource access authorizations for theprimary account such as an Open Authorization (OAuth) configuration; andan authentication configuration that defines access credentialauthentication features for the primary account such as a SecurityAssertion Markup Language (SAML) Single Sign-On (SSO) configuration. Thedata platform uses the account data to replicate the primary account,which results in the secondary account.

When replicating the primary account, the data platform automaticallyreplicates the security configurations of the primary account to thesecondary account. In replicating the security configurations, the dataplatform replicates the identity management configuration and configuresan access token associated with the identity management configurationfor validation by the secondary account. The data platform alsoreplicates the authorization configuration and configures a refreshtoken associated with the authorization configuration for validation bythe secondary account. In addition, the data platform automaticallyreplicates the authentication configuration to the secondary account.

This approach to account replication supports complicatedreplication/failover scenarios. For example, suppose there are multipleaccounts in a replication group that form a complicated replicationtopology such as a chain, a star, or even a loop. All tokens andsecurity configurations generated during the replication/failoverprocess are maintained. A security token generation process may involvemultiple objects from an account, such as a user, a securityintegration, a key, a role, and the like. The account replicationapproach described herein can make use of the objects replicated fromdifferent accounts to generate security tokens, and these tokens arestill valid after subsequent replications.

FIG. 1 illustrates an example computing environment 100 that includes adata platform 102 in communication with a client device 112, inaccordance with some embodiments of the present disclosure. To avoidobscuring the inventive subject matter with unnecessary detail, variousfunctional components that are not germane to conveying an understandingof the inventive subject matter have been omitted from FIG. 1 . However,a skilled artisan will readily recognize that various additionalfunctional components may be included as part of the computingenvironment 100 to facilitate additional functionality that is notspecifically described herein.

As shown, the data platform 102 comprises a database storage 104, acompute service manager 108, an execution platform 110, and a metadatadatabase 114. The database storage 104 comprises a plurality ofcomputing machines and provides on-demand computer system resources suchas data storage and computing power to the data platform 102. As shown,the database storage 104 comprises multiple data storage devices 106-1to 106-N. In some embodiments, the data storage devices 106-1 to 106-Nare cloud-based storage devices located in one or more geographiclocations. For example, the data storage devices 106-1 to 106-N may bepart of a public cloud infrastructure or a private cloud infrastructure.The data storage devices 106-1 to 106-N may be hard disk drives (HDDs),solid state drives (SSDs), storage clusters, Amazon S3™ storage systemsor any other data storage technology. Additionally, the database storage104 may include distributed file systems (e.g., Hadoop Distributed FileSystems (HDFS)), object storage systems, and the like.

The data platform 102 is used for reporting and analysis of integrateddata from one or more disparate sources including the storage devices106-1 to 106-N within the database storage 104. The data platform 102hosts and provides data reporting and analysis services to multiplecustomer accounts. Administrative users can create and manage identities(e.g., users, roles, and groups) and use permissions to allow or denyaccess to the identities to resources and services. Generally, the dataplatform 102 maintains numerous customer accounts for numerousrespective customers. The data platform 102 maintains each customeraccount in one or more storage devices of the database storage 104.Moreover, the data platform 102 may maintain metadata associated withthe customer accounts in the metadata database 114. Each customeraccount includes multiple data objects with examples including users,roles, permissions, stages, and the like.

The compute service manager 108 coordinates and manages operations ofthe data platform 102. The compute service manager 108 also performsquery optimization and compilation as well as managing clusters ofcompute services that provide compute resources (also referred to as“virtual warehouses”). The compute service manager 108 can support anynumber and type of clients such as end users providing data storage andretrieval requests, system administrators managing the systems andmethods described herein, and other components/devices that interactwith compute service manager 108. As an example, the compute servicemanager 108 is in communication with the client device 112. The clientdevice 112 can be used by a user of one of the multiple customeraccounts supported by the data platform 102 to interact with and utilizethe functionality of the data platform 102. In some embodiments, thecompute service manager 108 does not receive any direct communicationsfrom the client device 112 and only receives communications concerningjobs from a queue within the data platform 102.

The compute service manager 108 is also coupled to metadata database114. The metadata database 114 stores data pertaining to variousfunctions and aspects associated with the data platform 102 and itsusers. In some embodiments, the metadata database 114 includes a summaryof data stored in remote data storage systems as well as data availablefrom a local cache. Additionally, the metadata database 114 may includeinformation regarding how data is organized in remote data storagesystems (e.g., the database storage 104) and the local caches. Themetadata database 114 allows systems and services to determine whether apiece of data needs to be accessed without loading or accessing theactual data from a storage device.

The compute service manager 108 is further coupled to the executionplatform 110, which provides multiple computing resources that executevarious data storage and data retrieval tasks. The execution platform110 is coupled to the database storage 104. The execution platform 110comprises a plurality of compute nodes. A set of processes on a computenode executes a query plan compiled by the compute service manager 108.The set of processes can include: a first process to execute the queryplan; a second process to monitor and delete micro-partition files usinga least recently used (LRU) policy and implement an out of memory (OOM)error mitigation process; a third process that extracts healthinformation from process logs and status to send back to the computeservice manager 108; a fourth process to establish communication withthe compute service manager 108 after a system boot; and a fifth processto handle all communication with a compute cluster for a given jobprovided by the compute service manager 108 and to communicateinformation back to the compute service manager 108 and other computenodes of the execution platform 110.

In some embodiments, communication links between elements of thecomputing environment 100 are implemented via one or more datacommunication networks. These data communication networks may utilizeany communication protocol and any type of communication medium. In someembodiments, the data communication networks are a combination of two ormore data communication networks (or sub-networks) coupled to oneanother. In alternate embodiments, these communication links areimplemented using any type of communication medium and any communicationprotocol.

As shown in FIG. 1 , the data storage devices 106-1 to 106-N aredecoupled from the computing resources associated with the executionplatform 110. This architecture supports dynamic changes to the dataplatform 102 based on the changing data storage/retrieval needs as wellas the changing needs of the users and systems. The support of dynamicchanges allows the data platform 102 to scale quickly in response tochanging demands on the systems and components within the data platform102. The decoupling of the computing resources from the data storagedevices supports the storage of large amounts of data without requiringa corresponding large amount of computing resources. Similarly, thisdecoupling of resources supports a significant increase in the computingresources utilized at a particular time without requiring acorresponding increase in the available data storage resources.

The compute service manager 108, metadata database 114, executionplatform 110, and database storage 104 are shown in FIG. 1 as individualdiscrete components. However, each of the compute service manager 108,metadata database 114, execution platform 110, and database storage 104may be implemented as a distributed system (e.g., distributed acrossmultiple systems/platforms at multiple geographic locations).Additionally, each of the compute service manager 108, metadata database114, execution platform 110, and database storage 104 can be scaled upor down (independently of one another) depending on changes to therequests received and the changing needs of the data platform 102. Thus,in the described embodiments, the data platform 102 is dynamic andsupports regular changes to meet the current data processing needs.

During typical operation, the data platform 102 processes multiple jobsdetermined by the compute service manager 108. These jobs are scheduledand managed by the compute service manager 108 to determine when and howto execute the job. For example, the compute service manager 108 maydivide the job into multiple discrete tasks and may determine what datais needed to execute each of the multiple discrete tasks. The computeservice manager 108 may assign each of the multiple discrete tasks toone or more nodes of the execution platform 110 to process the task. Thecompute service manager 108 may determine what data is needed to processa task and further determine which nodes within the execution platform110 are best suited to process the task. Some nodes may have alreadycached the data needed to process the task and, therefore, be a goodcandidate for processing the task. Metadata stored in the metadatadatabase 114 assists the compute service manager 108 in determiningwhich nodes in the execution platform 110 have already cached at least aportion of the data needed to process the task. One or more nodes in theexecution platform 110 process the task using data cached by the nodesand, if necessary, data retrieved from the database storage 104. It isdesirable to retrieve as much data as possible from caches within theexecution platform 110 because the retrieval speed is typically muchfaster than retrieving data from the database storage 104.

As shown in FIG. 1 , the computing environment 100 separates theexecution platform 110 from the database storage 104. In thisarrangement, the processing resources and cache resources in theexecution platform 110 operate independently of the data storage devices106-1 to 106-N in the database storage 104. Thus, the computingresources and cache resources are not restricted to specific datastorage devices 106-1 to 106-N. Instead, all computing resources and allcache resources may retrieve data from, and store data to, any of thedata storage resources in the database storage 104.

FIG. 2 is a block diagram illustrating components of the compute servicemanager 108, in accordance with some embodiments of the presentdisclosure. As shown in FIG. 2 , the compute service manager 108includes an access manager 202 and a key manager 204 coupled to a datastorage device 206. Access manager 202 handles authentication andauthorization tasks for the systems described herein. Key manager 204manages storage and authentication of keys used during authenticationand authorization tasks. For example, access manager 202 and key manager204 manage the keys used to access data stored in remote storage devices(e.g., data storage devices in database storage 104). As used herein,the remote storage devices may also be referred to as “persistentstorage devices” or “shared storage devices.”

A request processing service 208 manages received data storage requestsand data retrieval requests (e.g., jobs to be performed on databasedata). For example, the request processing service 208 may determine thedata necessary to process a received query (e.g., a data storage requestor data retrieval request). The data may be stored in a cache within theexecution platform 110 or in a data storage device in database storage104.

A management console service 210 supports access to various systems andprocesses by administrators and other system managers. Additionally, themanagement console service 210 may receive a request to execute a joband monitor the workload on the system.

The compute service manager 108 also includes a job compiler 212, a joboptimizer 214, and a job executor 216. The job compiler 212 parses a jobinto multiple discrete tasks and generates the execution code for eachof the multiple discrete tasks. The job optimizer 214 determines thebest method to execute the multiple discrete tasks based on the datathat needs to be processed. The job optimizer 214 also handles variousdata pruning operations and other data optimization techniques toimprove the speed and efficiency of executing the job. The job executor216 executes the execution code for jobs received from a queue ordetermined by the compute service manager 108.

A job scheduler and coordinator 218 sends received jobs to theappropriate services or systems for compilation, optimization, anddispatch to the execution platform 110. For example, jobs may beprioritized and processed in that prioritized order. In an embodiment,the job scheduler and coordinator 218 determines a priority for internaljobs that are scheduled by the compute service manager 108 with other“outside” jobs such as user queries that may be scheduled by othersystems in the database but may utilize the same processing resources inthe execution platform 110. In some embodiments, the job scheduler andcoordinator 218 identifies or assigns particular nodes in the executionplatform 110 to process particular tasks. A virtual warehouse manager220 manages the operation of multiple virtual warehouses implemented inthe execution platform 110. As discussed below, each virtual warehouseincludes multiple execution nodes that each include a cache and aprocessor.

Additionally, the compute service manager 108 includes a configurationand metadata manager 222, which manages the information related to thedata stored in the remote data storage devices and in the local caches(e.g., the caches in execution platform 110). The configuration andmetadata manager 222 uses the metadata to determine which datamicro-partitions need to be accessed to retrieve data for processing aparticular task or job. A monitor and workload analyzer 224 overseesprocesses performed by the compute service manager 108 and manages thedistribution of tasks (e.g., workload) across the virtual warehouses andexecution nodes in the execution platform 110. The monitor and workloadanalyzer 224 also redistributes tasks, as needed, based on changingworkloads throughout the data platform 102 and may further redistributetasks based on a user (e.g., “external”) query workload that may also beprocessed by the execution platform 110. The configuration and metadatamanager 222 and the monitor and workload analyzer 224 are coupled to adata storage device 226. Data storage device 226 in FIG. 2 representsany data storage device within the data platform 102. For example, datastorage device 226 may represent caches in execution platform 110,storage devices in database storage 104, or any other storage device.

As shown, the compute service manager 108 further includes an accountreplication manager 228. The account replication manager 228 isresponsible for handling account replication including automaticreplication of security features. Further details regarding thegeneration of pruning indexes are discussed below.

FIG. 3 is a block diagram illustrating components of the executionplatform 110, in accordance with some embodiments of the presentdisclosure. As shown in FIG. 3 , the execution platform 110 includesmultiple virtual warehouses, including virtual warehouse 1, virtualwarehouse 2, and virtual warehouse n. Each virtual warehouse includesmultiple execution nodes that each includes a data cache and aprocessor. The virtual warehouses can execute multiple tasks in parallelby using the multiple execution nodes. As discussed herein, theexecution platform 110 can add new virtual warehouses and drop existingvirtual warehouses in real time based on the current processing needs ofthe systems and users. This flexibility allows the execution platform110 to quickly deploy large amounts of computing resources when neededwithout being forced to continue paying for those computing resourceswhen they are no longer needed. All virtual warehouses can access datafrom any data storage device (e.g., any storage device in databasestorage 104).

Although each virtual warehouse shown in FIG. 3 includes three executionnodes, a particular virtual warehouse may include any number ofexecution nodes. Further, the number of execution nodes in a virtualwarehouse is dynamic, such that new execution nodes are created whenadditional demand is present, and existing execution nodes are deletedwhen they are no longer necessary.

Each virtual warehouse is capable of accessing any of the data storagedevices 106-1 to 106-N shown in FIG. 1 . Thus, the virtual warehousesare not necessarily assigned to a specific data storage device 106-1 to106-N and, instead, can access data from any of the data storage devices106-1 to 106-N within the database storage 104. Similarly, each of theexecution nodes shown in FIG. 3 can access data from any of the datastorage devices 106-1 to 106-N. In some embodiments, a particularvirtual warehouse or a particular execution node may be temporarilyassigned to a specific data storage device, but the virtual warehouse orexecution node may later access data from any other data storage device.

In the example of FIG. 3 , virtual warehouse 1 includes three executionnodes 302-1, 302-2, and 302-N. Execution node 302-1 includes a cache304-1 and a processor 306-1. Execution node 302-2 includes a cache 304-2and a processor 306-2. Execution node 302-N includes a cache 304-N and aprocessor 306-N. Each execution node 302-1, 302-2, and 302-N isassociated with processing one or more data storage and/or dataretrieval tasks. For example, a virtual warehouse may handle datastorage and data retrieval tasks associated with an internal service,such as a clustering service, a materialized view refresh service, afile compaction service, a storage procedure service, or a file upgradeservice. In other implementations, a particular virtual warehouse mayhandle data storage and data retrieval tasks associated with aparticular data storage system or a particular category of data.

Similar to virtual warehouse 1 discussed above, virtual warehouse 2includes three execution nodes 312-1, 312-2, and 312-N. Execution node312-1 includes a cache 314-1 and a processor 316-1. Execution node 312-2includes a cache 314-2 and a processor 316-2. Execution node 312-Nincludes a cache 314-N and a processor 316-N. Additionally, virtualwarehouse N includes three execution nodes 322-1, 322-2, and 322-N.Execution node 322-1 includes a cache 324-1 and a processor 326-1.Execution node 322-2 includes a cache 324-2 and a processor 326-2.Execution node 322-N includes a cache 324-N and a processor 326-N.

In some embodiments, the execution nodes shown in FIG. 3 are statelesswith respect to the data the execution nodes are caching. For example,these execution nodes do not store or otherwise maintain stateinformation about the execution node or the data being cached by aparticular execution node. Thus, in the event of an execution nodefailure, the failed node can be transparently replaced by another node.Since there is no state information associated with the failed executionnode, the new (replacement) execution node can easily replace the failednode without concern for recreating a particular state.

Although the execution nodes shown in FIG. 3 each includes one datacache and one processor, alternate embodiments may include executionnodes containing any number of processors and any number of caches.Additionally, the caches may vary in size among the different executionnodes. The caches shown in FIG. 3 store, in the local execution node,data that was retrieved from one or more data storage devices indatabase storage 104. Thus, the caches reduce or eliminate thebottleneck problems occurring in platforms that consistently retrievedata from remote storage systems. Instead of repeatedly accessing datafrom the remote storage devices, the systems and methods describedherein access data from the caches in the execution nodes, which issignificantly faster and avoids the bottleneck problem discussed above.In some embodiments, the caches are implemented using high-speed memorydevices that provide fast access to the cached data. Each cache canstore data from any of the storage devices in the database storage 104.

Further, the cache resources and computing resources may vary betweendifferent execution nodes. For example, one execution node may containsignificant computing resources and minimal cache resources, making theexecution node useful for tasks that require significant computingresources. Another execution node may contain significant cacheresources and minimal computing resources, making this execution nodeuseful for tasks that require caching of large amounts of data. Yetanother execution node may contain cache resources providing fasterinput-output operations, useful for tasks that require fast scanning oflarge amounts of data. In some embodiments, the cache resources andcomputing resources associated with a particular execution node aredetermined when the execution node is created, based on the expectedtasks to be performed by the execution node.

Additionally, the cache resources and computing resources associatedwith a particular execution node may change over time based on changingtasks performed by the execution node. For example, an execution nodemay be assigned more processing resources if the tasks performed by theexecution node become more processor-intensive. Similarly, an executionnode may be assigned more cache resources if the tasks performed by theexecution node require a larger cache capacity.

Although virtual warehouses 1, 2, and N are associated with the sameexecution platform 110, the virtual warehouses may be implemented usingmultiple computing systems at multiple geographic locations. Forexample, virtual warehouse 1 can be implemented by a computing system ata first geographic location, while virtual warehouses 2 and N areimplemented by another computing system at a second geographic location.In some embodiments, these different computing systems are cloud-basedcomputing systems maintained by one or more different entities.

Additionally, each virtual warehouse is shown in FIG. 3 as havingmultiple execution nodes. The multiple execution nodes associated witheach virtual warehouse may be implemented using multiple computingsystems at multiple geographic locations. For example, an instance ofvirtual warehouse 1 implements execution nodes 302-1 and 302-2 on onecomputing platform at a geographic location and implements executionnode 302-N at a different computing platform at another geographiclocation. Selecting particular computing systems to implement anexecution node may depend on various factors, such as the level ofresources needed for a particular execution node (e.g., processingresource requirements and cache requirements), the resources availableat particular computing systems, communication capabilities of networkswithin a geographic location or between geographic locations, and whichcomputing systems are already implementing other execution nodes in thevirtual warehouse.

A particular execution platform 110 may include any number of virtualwarehouses. Additionally, the number of virtual warehouses in aparticular execution platform is dynamic, such that new virtualwarehouses are created when additional processing and/or cachingresources are needed. Similarly, existing virtual warehouses may bedeleted when the resources associated with the virtual warehouse are nolonger necessary.

In some embodiments, the virtual warehouses may operate on the same datain database storage 104, but each virtual warehouse has its ownexecution nodes with independent processing and caching resources. Thisconfiguration allows requests on different virtual warehouses to beprocessed independently and with no interference between the requests.This independent processing, combined with the ability to dynamicallyadd and remove virtual warehouses, supports the addition of newprocessing capacity for new users without impacting the performanceobserved by the existing users.

FIG. 4 is a conceptual diagram illustrating various customer accountreplication groups, in accordance with some embodiments of the presentdisclosure. A replication group refers to a group of customer accountsthat includes a primary account and one or more secondary accounts thatare produced by replicating the primary account. In the context of areplication group, a secondary account can, in some instances, becomethe primary account for the replication group with which the customercommunicates. The data platform 102 can use a replication groupidentifier to identify accounts that are part of the same replicationgroup.

As noted above, each customer account includes multiple data objectswith examples including users, roles, permissions, stages, and the like.Additionally, a customer account may include one or more securityconfigurations. The one or more security configurations can include anidentity management (e.g., SCIM) configuration, an authorization (e.g.,OAuth) configuration, and an authentication (e.g., SAML SSO)configuration, among others. Each security configuration can include oneor more integrations, which are objects that provide an interfacebetween the data platform 102 and a third-party service. For example, acustomer account may include: a first integration object that providesan interface with a third-party identity management service (e.g.,SCIM); a second integration object that provides an interface with athird-party authorization service (e.g., OAuth); and a third integrationthat provides an interface with a third-party authentication service(e.g., SAML SSO).

An account can be replicated from one deployment to another deploymentor within the same deployment. In addition, as shown in FIG. 4 ,multiple accounts in the same replication group can be replicatedto/from each other and therefore create various topologies such as astar 410, a chain 420, or a loop 430. Regardless of the topology, thedata platform 102 replicates accounts such that all securityconfigurations are inherited from its ancestor accounts and alllong-lived security tokens generated by ancestor accounts can bevalidated by the replicated account.

FIGS. 5-8 are flow diagrams illustrating operations of the network-baseddata platform 102 in performing a method 500 for customer accountreplication, in accordance with some embodiments of the presentdisclosure. The method 500 may be embodied in computer-readableinstructions for execution by one or more hardware components (e.g., oneor more processors) such that the operations of the method 500 may beperformed by components of data platform 102. Accordingly, the method500 is described below, by way of example with reference thereto.However, it shall be appreciated that method 500 may be deployed onvarious other hardware configurations and is not intended to be limitedto deployment within the data platform 102.

Depending on the embodiment, an operation of the method 500 may berepeated in different ways or involve intervening operations not shown.Though the operations of the method 500 may be depicted and described ina certain order, the order in which the operations are performed mayvary among embodiments, including performing certain operations inparallel or performing sets of operations in separate processes.

At operation 505, the compute service manager 108 receives a request toreplicate an account maintained by the data platform 102 (hereinafterreferred to as a “primary account”). The request can be received fromclient device 112 or from a programmatic client of the data platform102.

At operation 510, the compute service manager 108 accesses account dataassociated with the primary account from a database (e.g., metadatadatabase 114 and/or a database maintained in the database storage 104).The account data describes various aspects of the primary account. Theaccount data can include account-level objects such as users, roles, andthe like, as well as one or more security configurations. The securityconfigurations for the primary account can include an identitymanagement configuration (e.g., a SCIM configuration), an authorizationconfiguration (e.g., an OAuth configuration), and an authenticationconfiguration (e.g., a SAML SSO configuration). Each securityconfiguration can include one or more integration objects to provide aninterface with a corresponding third-party service, as noted above.

In response to the request, the compute service manager 108 replicatesthe primary account using the account data, at operation 515. Inreplicating the primary account, the compute service manager 108generates a secondary account (also referred to herein as a “replicatedaccount”). In replicating the primary account to the secondary account,the compute service manager 108 automatically replicates the securityconfigurations of the primary account to the secondary account. Asshown, the operations 520, 525, 530, 535, and 540 can be performed aspart of replicating the account and specifically as part of replicatingthe security configurations of the primary account.

At operation 520, the compute service manager 108 replicates an identitymanagement configuration (e.g., a SCIM configuration) of the primaryaccount. At operation 525, the compute service manager 108 configures anaccess token associated with the identity management configuration sothat the access token can be validated by the secondary account. Furtherdetails regarding operations 520 and 525 are discussed below inreference to FIG. 6 .

At operation 530, the compute service manager 108 replicates anauthorization configuration (e.g., an OAuth configuration) of theaccount. At operation 535, the compute service manager 108 configures arefresh token associated with the authorization configuration so thatthe access token can be validated by the secondary account. Furtherdetails regarding operations 530 and 535 are discussed below inreference to FIG. 7 .

At operation 540, the compute service manager 108 replicates anauthentication configuration of the account (e.g., a SAML SSOconfiguration). Further details regarding operation 540 are discussedbelow in reference to FIG. 8 .

As shown in FIG. 6 , the method 500 can include operations 605, 610,615, 620, 625, and 630. The operations 605, 610, and 615 can beperformed as part of operation 520 where the compute service manager 108replicates the identity management configuration of the account. Atoperation 605, the compute service manager 108 replicates a provisionerrole of the identity management configuration along with itspermissions. As a result, a replicated provisioner role is produced. Theprovisioner role for the primary account has associated permissions togrant new users and roles in the primary account. The replicatedprovisional role for the secondary account has associated permissions togrant new users and roles in the secondary account. The replicating ofthe provisioner role from the primary account results in creation of areplicated provisioner role.

At operation 610, the compute service manager 108 replicates anintegration object associated with the identity management configuration(hereinafter referred to also as a “primary integration object”). Theprimary integration object associated with the identity managementconfiguration provides an interface between the data platform 102 and athird-party identity management service that corresponds to the identitymanagement configuration of the primary account. In replicating theprimary integration object, the compute service manager 108 generates asecondary integration object (also referred to as a “replicatedintegration object”).

The primary integration object includes a field that identifies a rolein the primary account used to execute the integration with thethird-party identity management service. When the secondary integrationobject is initially created through replication of the primaryintegration object, the field is empty. Accordingly, at operation 615,the compute service manager 108 connects the replicated provisioner roleto the replicated integration object. In doing so, the compute servicemanager 108 may remap an identifier of the replicated provisioner roleto the replicated integration object.

As shown, the operations 620, 625, 630, and 635 can be performed as partof operation 525 where the compute service manager 108 configures theaccess token associated with the identity management configuration foruse by the secondary account. At operation 620, the compute servicemanager 108 modifies a string structure of the access token. Inmodifying the string structure, the compute service manager 108 performsa number of operations including: changing a schema version number;adding a new deployment identifier that is outside of an encryptionstring portion of the string; adding integration issuing informationthat includes the deployment identifier and an integration sourceidentifier; and adding a replication group identifier in the encryptionstring portion.

At operation 625, the compute service manager 108 modifies a datastructure of the access token. The compute service manager 108 modifiesthe data structure to include a global identifier. The global identifiercomprises a combination of a deployment identifier and an entityidentifier. The deployment identifier identifies the deployment for theprimary account, and the entity identifier identifies a customer entitythat corresponds to the primary account. In addition, the computeservice manager 108 may further modify the data structure by adding anorganization name into the attributes of the data structure and add anidentifier of an issuing deployment and version.

At operation 630, the compute service manager 108 replicates one or moretoken encryption keys used to encrypt the access token. The one or morereplicated token encryption keys may be stored in a data object thatincludes metadata associated with the secondary account. In someinstances, the compute service manager 108 can perform key cleaning orremoval so as not to store keys in the secondary account indefinitely.In performing a cleaning operation on a key, the compute service manager108 may remove a key from the data object associated with the account(primary or secondary) and add the key to a list of expired keys that isused by a key expiration service to delete expired keys. The computeservice manager 108 may perform a key cleaning, for example, when: acustomer suspends a replication of a first account to a second account;when a customer disables replication of a replication group from a firstaccount to a second account by removing the second account from anallowed list; or when a customer disables a failover group from a firstaccount to a second account by removing the second account from theallowed list.

At operation 635, the compute service manager 108 modifies a format of auser identifier associated with the access token. Initially, a useridentifier is generated when a new user is provisioned. The useridentifier comprises an account identifier, a local entity identifier,and a 2-bit flag. In modifying the identifier format, the computeservice manager 108 changes the local entity identifier to the globalidentifier discussed above.

As shown in FIG. 7 , the method 500 can include operations 705, 710,715, 720, 725, 730, 735, and 740. The operations 705, 710, 715, 720,725, and 730 can be performed as part of the operation 530 where thecompute service manager 108 replicates the authentication configurationof the account. At operation 705, the compute service manager 108replicates one or more integration objects associated with theauthorization configuration. Each such integration object provides aninterface between the data platform 102 and a third-party authorizationservice (e.g., OAuth) that corresponds to the authorizationconfiguration. The compute service manager 108 can replicate a system(internal) integration object, a client (external) integration object,or both depending on the circumstances. In instances in which both thesystem and client integration object are replicated, the compute servicemanager 108 replicates both integration objects to include the sameclient identifier and client secret.

The compute service manager 108 further replicates a user associatedwith the authorization configuration (operation 710), a role associatedwith the authorization configuration (operation 715), and anauthorization consent of the authorization configuration (operation720). The authorization consent corresponds to a stored indication thatthe user consents to use of the role in a session. At operation 725, thecompute service manager 108 links the authorization consent to theintegration objects, the user, and the role.

The operations 730, 735, and 740 can be performed as part of operation535 where the compute service manager 108 configures the refresh tokenassociated with the authorization configuration for use with thesecondary account. At operation 730, the compute service manager 108modifies a token string structure of the refresh token. In modifying thetoken string structure, the compute service manager 108 may perform oneor more of: changing a version number, adding a deployment identifiercorresponding to the deployment from where the fresh token is generated;adding the global identifier into an encrypted string portion; andadding a replication group identifier into the encrypted string portion.

At operation 735, the compute service manager 108 modifies a datastructure of the refresh token. The compute service manager 108 modifiesthe data structure to include the global identifier mentioned above. Atoperation 740, the compute service manager 108 replicates one or moretoken encryption keys used to encrypt the refresh token.

As shown in FIG. 8 , the method 500 can, in some embodiments, includeoperations 805 and 810. Consistent with these embodiments, theoperations 805 and 810 can be performed as part of the operation 540where the compute service manager 108 replicates the authorizationconfiguration.

At operation 805, the compute service manager 108 replicates anintegration object associated with the authorization configuration. Theintegration object provides an interface between the data platform 102and a third-party authorization service corresponding to theauthorization configuration. In replicating the security integrationobject, the compute service manager 108 generates a replicated securityintegration object. At operation 810, the compute service manager 108configures the new security integration object to include a globalaccount URL. The global account URL corresponds to account resources(e.g., dashboards and other user interfaces) that can be utilized withinthe replication group. The inclusion of the global account URL in theintegration object allows account users to continue to seamlessly accesssuch resources upon a failover to the secondary account.

Described implementations of the subject matter can include one or morefeatures, alone or in combination as illustrated below by way ofexample.

Example 1 is a method comprising: receiving a request to replicate afirst account maintained by a data platform; accessing, based on therequest, account data associated with the first account, the accountdata comprising security configurations for the first account; and inresponse to the request, replicating, by one or more hardwareprocessors, the first account using the account data, the replicating ofthe first account resulting in a second account, the replicating of thefirst account comprising automatically replicating the securityconfigurations for the first account to the second account, thereplicating of the security configurations comprising: replicating anidentity management configuration of the first account to the secondaccount; replicating an authorization configuration of the first accountto the second account; and replicating an authentication configurationof the first account to the second account.

Example 2 includes the method of Example 1, wherein the replicating ofthe security configurations further comprises configuring an accesstoken associated with the identity management configuration forvalidation by the second account.

Example 3 includes the method of any one or more of Examples 1 or 2,wherein configuring the access token associated with the identitymanagement configuration comprises modifying a data structure of theaccess token to include a global identifier.

Example 4 includes the method of any one or more of Examples 1-3,wherein the configuring of the access token further comprises: modifyinga string structure of the access token to include a replication groupidentifier, the replication group identifier identifying a group ofaccounts, the group of accounts including the first account and thesecond account; replicating a token encryption key used to encrypt theaccess token; and modifying an identifier format associated with theaccess token to include the global identifier.

Example 5 includes the method of any one or more of Examples 1-4,wherein the global identifier comprises a combination of a deploymentidentifier and an entity identifier, the deployment identifieridentifying a deployment of the first account, the entity identifieridentifying a customer entity corresponding to the first account.

Example 6 includes the method of any one or more of Examples 1-5,wherein the replicating of the identity management configurationcomprises: replicating a provisioner role in the identity managementconfiguration, the provisioner role having associated permissions toprovision new users and roles within the first account, the replicatingof the provisioner role resulting in a replicated provisioner rolehaving associated permissions to provision new users and roles withinthe second account; replicating an integration object associated withthe identity management configuration, the integration object providingan interface between the data platform and an identity managementservice corresponding to the identity management configuration; andconnecting the provisioner role with the integration object.

Example 7 includes the method of any one or more of Examples 1-6,wherein the replicating of the security configurations further comprisesconfiguring a refresh token associated with the authorizationconfiguration for validation by the second account.

Example 8 includes the method of any one or more of Examples 1-7,wherein configuring of the refresh token comprises modifying a datastructure of the refresh token to include a global identifier, theglobal identifier comprising a combination of a deployment identifierand an entity identifier, the deployment identifier identifying adeployment of the first account, the entity identifier identifying acustomer entity corresponding to the first account.

Example 9 includes the method of any one or more of Examples 1-8,wherein the configuring of the refresh token further comprises:modifying a string structure of the refresh token to include the globalidentifier and a replication group identifier, the replication groupidentifier identifying a group of accounts, the group of accountsincluding the first account and the second account; and replicating atoken encryption key used to encrypt the refresh token.

Example 10 includes the method of any one or more of Examples 1-9,wherein the replicating of the authorization configuration of the firstaccount comprises: replicating an integration object associated with theauthorization configuration, the integration object providing aninterface between the data platform and an authorization servicecorresponding to the authorization configuration; replicating a user inthe authorization configuration; replicating a role in the authorizationconfiguration; replicating an authorization consent in the authorizationconfiguration; and linking the authorization consent with theintegration object, the user, and the role.

Example 11 includes the method of any one or more of Examples 1-10,wherein replicating the authentication configuration of the firstaccount comprises: replicating an integration object associated with theauthentication configuration, the integration object providing aninterface between the data platform and an authentication serviceassociated with the authentication configuration, the replicating of theintegration object resulting in a replicated integration object; andconfiguring the replicated integration object to include a globalaccount uniform resource locator (URL).

Example 12 includes the method of any one or more of Examples 1-11,wherein: the identity management configuration comprises a System forCross-domain Identity Management (SCIM) configuration; the authorizationconfiguration comprises an Open Authorization (OAuth) configuration; andthe authentication configuration corresponds to a security assertionmarkup language (SAML) single sign-on (S SO) configuration.

Example 13. A system comprising: one or more processors of a machine;and at least one memory storing instructions that, when executed by theone or more processors, cause the machine to perform operationsimplementing any one of example methods 1 to 12.

Example 14. A machine-readable storage device embodying instructionsthat, when executed by a machine, cause the machine to performoperations implementing any one of example methods 1 to 13.

FIG. 9 illustrates a diagrammatic representation of a machine 900 in theform of a computer system within which a set of instructions may beexecuted for causing the machine 900 to perform any one or more of themethodologies discussed herein, according to an example embodiment.Specifically, FIG. 9 shows a diagrammatic representation of the machine900 in the example form of a computer system, within which instructions916 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 900 to perform any one ormore of the methodologies discussed herein may be executed. For example,the instructions 916 may cause the machine 900 to execute any one ormore operations of any one or more of the method 500. In this way, theinstructions 916 transform a general, non-programmed machine into aparticular machine 900 (e.g., the compute service manager 108, theexecution platform 110, and the data storage devices 206) that isspecially configured to carry out any one of the described andillustrated functions in the manner described herein.

In alternative embodiments, the machine 900 operates as a standalonedevice or may be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 900 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 900 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a smart phone, a mobiledevice, a network router, a network switch, a network bridge, or anymachine capable of executing the instructions 916, sequentially orotherwise, that specify actions to be taken by the machine 900. Further,while only a single machine 900 is illustrated, the term “machine” shallalso be taken to include a collection of machines 900 that individuallyor jointly execute the instructions 916 to perform any one or more ofthe methodologies discussed herein.

The machine 900 includes processors 910, memory 930, and input/output(I/O) components 950 configured to communicate with each other such asvia a bus 902. In an example embodiment, the processors 910 (e.g., acentral processing unit (CPU), a reduced instruction set computing(RISC) processor, a complex instruction set computing (CISC) processor,a graphics processing unit (GPU), a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), a radio-frequencyintegrated circuit (RFIC), another processor, or any suitablecombination thereof) may include, for example, a processor 912 and aprocessor 914 that may execute the instructions 916. The term“processor” is intended to include multi-core processors 910 that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions 916 contemporaneously. AlthoughFIG. 9 shows multiple processors 910, the machine 900 may include asingle processor with a single core, a single processor with multiplecores (e.g., a multi-core processor), multiple processors with a singlecore, multiple processors with multiple cores, or any combinationthereof.

The memory 930 may include a main memory 932, a static memory 934, and astorage unit 936, all accessible to the processors 910 such as via thebus 902. The main memory 932, the static memory 934, and the storageunit 936 store the instructions 916 embodying any one or more of themethodologies or functions described herein. The instructions 916 mayalso reside, completely or partially, within the main memory 932, withinthe static memory 934, within the storage unit 936, within at least oneof the processors 910 (e.g., within the processor's cache memory), orany suitable combination thereof, during execution thereof by themachine 900.

The I/O components 950 include components to receive input, provideoutput, produce output, transmit information, exchange information,capture measurements, and so on. The specific I/O components 950 thatare included in a particular machine 900 will depend on the type ofmachine. For example, portable machines such as mobile phones willlikely include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 950 mayinclude many other components that are not shown in FIG. 9 . The I/Ocomponents 950 are grouped according to functionality merely forsimplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 950 mayinclude output components 952 and input components 954. The outputcomponents 952 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), other signal generators, and soforth. The input components 954 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or another pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 950 may include communication components 964 operableto couple the machine 900 to a network 980 or devices 970 via a coupling982 and a coupling 972, respectively. For example, the communicationcomponents 964 may include a network interface component or anothersuitable device to interface with the network 980. In further examples,the communication components 964 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, and other communication components to provide communicationvia other modalities. The devices 970 may be another machine or any of awide variety of peripheral devices (e.g., a peripheral device coupledvia a universal serial bus (USB)). For example, as noted above, themachine 900 may correspond to any one of the compute service manager108, the execution platform 110, and the devices 970 may include thedata storage device 206 or any other computing device described hereinas being in communication with the data platform 102 or the databasestorage 104.

The various memories (e.g., 930, 932, 934, and/or memory of theprocessor(s) 910 and/or the storage unit 936) may store one or more setsof instructions 916 and data structures (e.g., software) embodying orutilized by any one or more of the methodologies or functions describedherein. These instructions 916, when executed by the processor(s) 910,cause various operations to implement the disclosed embodiments.

As used herein, the terms “machine-storage medium,” “device-storagemedium,” and “computer-storage medium” mean the same thing and may beused interchangeably in this disclosure. The terms refer to a single ormultiple storage devices and/or media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storeexecutable instructions and/or data. The terms shall accordingly betaken to include, but not be limited to, solid-state memories, andoptical and magnetic media, including memory internal or external toprocessors. Specific examples of machine-storage media, computer-storagemedia, and/or device-storage media include non-volatile memory,including by way of example semiconductor memory devices, e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), field-programmable gate arrays(FPGAs), and flash memory devices; magnetic disks such as internal harddisks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The terms “machine-storage media,” “computer-storage media,” and“device-storage media” specifically exclude carrier waves, modulateddata signals, and other such media, at least some of which are coveredunder the term “signal medium” discussed below.

In various example embodiments, one or more portions of the network 980may be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local-area network (LAN), a wireless LAN (WLAN), awide-area network (WAN), a wireless WAN (WWAN), a metropolitan-areanetwork (MAN), the Internet, a portion of the Internet, a portion of thepublic switched telephone network (PSTN), a plain old telephone service(POTS) network, a cellular telephone network, a wireless network, aWi-Fi® network, another type of network, or a combination of two or moresuch networks. For example, the network 980 or a portion of the network980 may include a wireless or cellular network, and the coupling 982 maybe a Code Division Multiple Access (CDMA) connection, a Global Systemfor Mobile communications (GSM) connection, or another type of cellularor wireless coupling. In this example, the coupling 982 may implementany of a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High-Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard-setting organizations, other long-rangeprotocols, or other data transfer technology.

The instructions 916 may be transmitted or received over the network 980using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components964) and utilizing any one of a number of well-known transfer protocols(e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions916 may be transmitted or received using a transmission medium via thecoupling 972 (e.g., a peer-to-peer coupling) to the devices 970. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure. The terms “transmissionmedium” and “signal medium” shall be taken to include any intangiblemedium that is capable of storing, encoding, or carrying theinstructions 916 for execution by the machine 900, and include digitalor analog communications signals or other intangible media to facilitatecommunication of such software. Hence, the terms “transmission medium”and “signal medium” shall be taken to include any form of modulated datasignal, carrier wave, and so forth. The term “modulated data signal”means a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in the signal.

The terms “machine-readable medium,” “computer-readable medium,” and“device-readable medium” mean the same thing and may be usedinterchangeably in this disclosure. The terms are defined to includeboth machine-storage media and transmission media. Thus, the termsinclude both storage devices/media and carrier waves/modulated datasignals.

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Similarly, the methods described hereinmay be at least partially processor-implemented. For example, at leastsome of the operations of the method 500 may be performed by one or moreprocessors. The performance of certain of the operations may bedistributed among the one or more processors, not only residing within asingle machine, but also deployed across a number of machines. In someexample embodiments, the processor or processors may be located in asingle location (e.g., within a home environment, an office environment,or a server farm), while in other embodiments the processors may bedistributed across a number of locations.

Although the embodiments of the present disclosure have been describedwith reference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader scope of the inventive subjectmatter. Accordingly, the specification and drawings are to be regardedin an illustrative rather than a restrictive sense. The accompanyingdrawings that form a part hereof show, by way of illustration, and notof limitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be used and derived therefrom,such that structural and logical substitutions and changes may be madewithout departing from the scope of this disclosure. This DetailedDescription, therefore, is not to be taken in a limiting sense, and thescope of various embodiments is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent, to those of skill inthe art, upon reviewing the above description.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Also, in the following claims, theterms “including” and “comprising” are open-ended; that is, a system,device, article, or process that includes elements in addition to thoselisted after such a term in a claim is still deemed to fall within thescope of that claim.

What is claimed is:
 1. A data platform comprising: at least one hardwareprocessor; and at least one memory storing instructions that cause theat least one hardware processor to perform operations comprising:receiving a request to replicate a first account maintained by the dataplatform; accessing, based on the request, account data associated withthe first account, the account data comprising one or more securityconfigurations for the first account; and in response to the request,replicating the first account using the account data, the replicating ofthe first account resulting in a second account, the replicating of thefirst account comprising automatically replicating the one or moresecurity configurations for the first account to the second account, thereplicating the one or more security configurations for the firstaccount comprising replicating at least one of an identity managementconfiguration, an authorization configuration, or an authenticationconfiguration to the second account.
 2. The data platform of claim 1,wherein the replicating of the one or more security configurationsfurther comprises configuring an access token associated with theidentity management configuration for validation by the second account.3. The data platform of claim 2, wherein configuring the access tokenassociated with the identity management configuration comprisesmodifying a data structure of the access token to include a globalidentifier.
 4. The data platform of claim 3, wherein the configuring ofthe access token further comprises: modifying a string structure of theaccess token to include a replication group identifier, the replicationgroup identifier identifying a group of accounts, the group of accountsincluding the first account and the second account; replicating a tokenencryption key used to encrypt the access token; and modifying anidentifier format associated with the access token to include the globalidentifier.
 5. The data platform of claim 3, wherein the globalidentifier comprises a combination of a deployment identifier and anentity identifier, the deployment identifier identifying a deployment ofthe first account, the entity identifier identifying a customer entitycorresponding to the first account.
 6. The data platform of claim 1,wherein the replicating of the identity management configurationcomprises: replicating a provisioner role in the identity managementconfiguration, the provisioner role having associated permissions toprovision new users and roles within the first account, the replicatingof the provisioner role resulting in a replicated provisioner rolehaving associated permissions to provision new users and roles withinthe second account; replicating an integration object associated withthe identity management configuration, the integration object providingan interface between the data platform and an identity managementservice corresponding to the identity management configuration; andconnecting the provisioner role with the integration object.
 7. The dataplatform of claim 1, wherein the replicating of the one or more securityconfigurations further comprises configuring a refresh token associatedwith the authorization configuration for validation by the secondaccount.
 8. The data platform of claim 7, wherein configuring of therefresh token comprises modifying a data structure of the refresh tokento include a global identifier, the global identifier comprising acombination of a deployment identifier and an entity identifier, thedeployment identifier identifying a deployment of the first account, theentity identifier identifying a customer entity corresponding to thefirst account.
 9. The data platform of claim 8, wherein the configuringof the refresh token further comprises: modifying a string structure ofthe refresh token to include the global identifier and a replicationgroup identifier, the replication group identifier identifying a groupof accounts, the group of accounts including the first account and thesecond account; and replicating a token encryption key used to encryptthe refresh token.
 10. The data platform of claim 8, wherein thereplicating of the authorization configuration comprises: replicating anintegration object associated with the authorization configuration, theintegration object providing an interface between the data platform andan authorization service corresponding to the authorizationconfiguration; replicating a user in the authorization configuration;replicating a role in the authorization configuration; replicating anauthorization consent in the authorization configuration; and linkingthe authorization consent with the integration object, the user, and therole.
 11. The data platform of claim 1, wherein replicating theauthentication configuration comprises: replicating an integrationobject associated with the authentication configuration, the integrationobject providing an interface between the data platform and anauthentication service associated with the authentication configuration,the replicating of the integration object resulting in a replicatedintegration object; and configuring the replicated integration object toinclude a global account uniform resource locator (URL).
 12. A methodcomprising: receiving a request to replicate a first account maintainedby a data platform; accessing, based on the request, account dataassociated with the first account, the account data comprising one ormore security configurations for the first account; and in response tothe request, replicating, by one or more hardware processors, the firstaccount using the account data, the replicating of the first accountresulting in a second account, the replicating of the first accountcomprising automatically replicating the one or more securityconfigurations for the first account to the second account, thereplicating the one or more security configurations for the firstaccount comprising replicating at least one of an identity managementconfiguration, an authorization configuration, or an authenticationconfiguration to the second account.
 13. The method of claim 12, whereinthe replicating of the one or more security configurations furthercomprises configuring an access token associated with the identitymanagement configuration for validation by the second account, whereinconfiguring the access token associated with the identity managementconfiguration comprises modifying a data structure of the access tokento include a global identifier.
 14. The method of claim 13, wherein theconfiguring of the access token further comprises: modifying a stringstructure of the access token to include a replication group identifier,the replication group identifier identifying a group of accounts, thegroup of accounts including the first account and the second account;replicating a token encryption key used to encrypt the access token; andmodifying an identifier format associated with the access token toinclude the global identifier.
 15. The method of claim 12, wherein thereplicating of the identity management configuration comprises:replicating a provisioner role in the identity management configuration,the provisioner role having associated permissions to provision newusers and roles within the first account, the replicating of theprovisioner role resulting in a replicated provisioner role havingassociated permissions to provision new users and roles within thesecond account; replicating an integration object associated with theidentity management configuration, the integration object providing aninterface between the data platform and an identity management servicecorresponding to the identity management configuration; and connectingthe provisioner role with the integration object.
 16. The method ofclaim 12, wherein the replicating of the one or more securityconfigurations further comprises configuring a refresh token associatedwith the authorization configuration for validation by the secondaccount.
 17. The method of claim 16, wherein configuring of the refreshtoken comprises modifying a data structure of the refresh token toinclude a global identifier, the global identifier comprising acombination of a deployment identifier and an entity identifier, thedeployment identifier identifying a deployment of the first account, theentity identifier identifying a customer entity corresponding to thefirst account.
 18. The method of claim 17, wherein the replicating ofthe authorization configuration comprises: replicating an integrationobject associated with the authorization configuration, the integrationobject providing an interface between the data platform and anauthorization service corresponding to the authorization configuration;replicating a user in the authorization configuration; replicating arole in the authorization configuration; replicating an authorizationconsent in the authorization configuration; and linking theauthorization consent with the integration object, the user, and therole.
 19. The method of claim 12, wherein replicating the authenticationconfiguration comprises: replicating an integration object associatedwith the authentication configuration, the integration object providingan interface between the data platform and an authentication serviceassociated with the authentication configuration, the replicating of theintegration object resulting in a replicated integration object; andconfiguring the replicated integration object to include a globalaccount uniform resource locator (URL).
 20. A computer-storage mediumcomprising instructions that, when executed by one or more processors ofa machine, configure the machine to perform operations comprising:receiving a request to replicate a first account maintained by a dataplatform; accessing, based on the request, account data associated withthe first account, the account data comprising one or more securityconfigurations for the first account; and in response to the request,replicating, by one or more hardware processors, the first account usingthe account data, the replicating of the first account resulting in asecond account, the replicating of the first account comprisingautomatically replicating the one or more security configurations forthe first account to the second account.